Summary

Update the consistency guide so its description of read-your-write and monotonic-read behavior matches what the client actually does on db:// remote-table connections.

Changes

• Note that read_consistency_interval applies to all db:// remote-table connections.
• Replace the version-pinning description with the timestamp-floor model that is now used for read-your-write across writes, checkout_latest, and restore.
• Mention that the freshness floor is shared across handles to the same table on the same connection.
• Document the per-handle monotonic-read watermark that prevents successive reads from observing an older version when traffic is load-balanced across query nodes, and note that checkout_latest resets it.

Context

Triggered by upstream changes that bring read-freshness signaling to the lance-namespace path of db:// connections and add a per-session monotonic-read watermark on remote tables, so the client behavior described in the docs now holds uniformly for remote tables.

Update history

• Initial: clarified read_consistency_interval for db:// remote tables and the timestamp-floor read-your-write model (feat: send read-freshness signal on the lance-namespace path lancedb#3551).
• Added a note that remote table handles now provide monotonic reads via a version watermark, reset on checkout_latest (feat(remote): monotonic reads via x-lancedb-min-read-version watermark lancedb#3597).